Skip to content

WIP: Add ipwatch controller to handle IP address changes#564

Closed
mangelajo wants to merge 3 commits into
openshift:mainfrom
mangelajo:dynamic-ip-changes
Closed

WIP: Add ipwatch controller to handle IP address changes#564
mangelajo wants to merge 3 commits into
openshift:mainfrom
mangelajo:dynamic-ip-changes

Conversation

@mangelajo

Copy link
Copy Markdown
Contributor

The IPWatchController will restart MicroShift when IP address
changes have been detected.

This is an initial implementation which will trigger the initialization
of all components with the new IP address and relies on systemd or
podman restarting the process.

Related-Issue: #556

Signed-off-by: Miguel Angel Ajo majopela@redhat.com

The IPWatchController will restart MicroShift when IP address
changes have been detected.

This is an initial implementation which will trigger the initialization
of all components with the new IP address and relies on systemd or
podman restarting the process.

Related-Issue: openshift#556

Signed-off-by: Miguel Angel Ajo <majopela@redhat.com>
@openshift-ci

openshift-ci Bot commented Jan 21, 2022

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from mangelajo after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mangelajo mangelajo changed the title Add ipwatch controller to handle IP address changes WIP: Add ipwatch controller to handle IP address changes Jan 21, 2022
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 21, 2022
@mangelajo mangelajo marked this pull request as draft January 21, 2022 15:23
This commit updates the openshift-apiserver and
openshift-oauth-apiserver when at microshift boot a new IP address is
detected or configured.

In addition, instead of following what kube-apiserver does with the
Endpoints, we just use the IP we want, kube-apiserver could need
some time to update endpoints at boot, and does not work well for
127.0.0.1 in our current configuration.

Close-Issue: openshift#556

Signed-off-by: Miguel Angel Ajo <majopela@redhat.com>
@fzdarsky

fzdarsky commented Jan 26, 2022

Copy link
Copy Markdown
Contributor

There already exists a mechanism for shutting down MicroShift and its embedded services, which is to cancel the context, either directly or via a SIGTERM sent to MicroShift. I believe we should reuse that mechanism rather than implementing a new + parallel mechanism.

Signed-off-by: Miguel Angel Ajo <majopela@redhat.com>
@oglok

oglok commented Apr 8, 2022

Copy link
Copy Markdown
Contributor

Closing this PR in favour of #650

@oglok oglok closed this Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants